Minutes, IBIS Quality Committee

18 Nov 2008

11-12 AM EST (8-9 AM PST)

ROLL CALL
  Adam Tambone
* Anders Ekholm, Ericsson
  Barry Katz, SiSoft
  Benny Lazer
  Benjamin P Silva
  Bob Cox, Micron
* Bob Ross, Teraspeed Consulting Group
  Brian Arsenault
  David Banas, Xilinx
* Eckhard Lenski, Nokia Siemens Networks
  Eric Brock
* Guan Tao, Huawei Technologies
  Gregory R Edlund
  Hazem Hegazy
  Huang Chunxing, Huawei Technologies
  John Figueroa
  John Angulo, Mentor Graphics
  Katja Koller, Nokia Siemens Networks
  Kevin Fisher
  Kim Helliwell, LSI Logic
  Lance Wang, IOMethodology
  Lynne Green
* Mike LaBonte, Cisco Systems
  Mike Mayer, SiSoft
* Moshiul Haque, Micron Technology
* Pavani Jella, TI
  Peter LaFlamme
  Randy Wolff, Micron Technology
  Radovan Vuletic, Qimonda
  Robert Haller, Enterasys
  Roy Leventhal, Leventhal Design & Communications
  Sherif Hammad, Mentor Graphics
  Todd Westerhoff, SiSoft
  Tom Dagostino, Teraspeed Consulting Group
  Kazuyoshi Shoji, Hitachi
  Sadahiro Nonoyama

Everyone in attendance marked by *

NOTE: "AR" = Action Required.

-----------------------MINUTES ---------------------------
Mike LaBonte conducted the meeting.

Call for patent disclosure:

- No one declared a patent.

AR Review:

- Mike propose IBISCHK bug for 5.5.6
  - TBD

New items:

Continued review of the IBIS Quality Specification:

5.5.7.	{LEVEL 2}  [Ramp] dV consistent with V-T table endpoints
- Bob: How about a [Ramp]dV/I-V check?
- Mike: That would fit into 5.5.6 better

5.5.6.	{LEVEL 2}  [Ramp] dV consistent with supply voltages
- Bob: Once IBISCHK has this we can drop it
- Mike: Would [Driver Schedule] and [Submodel] make it hard to calculate?
  - Bob: No, [Ramp] is for just the top buffer
- If this will be a new check, should we keep 5.5.6?
  - Anders: 5.5.6 is redundant if we have the new check
    - If IBISCHK implements it we do not need a new IQ
  - Moshiul: [Ramp] is not used when waveforms are there
  - We will keep this

5.5.7.	{LEVEL 2}  [Ramp] dV consistent with V-T table endpoints
- Mike: 50% accuracy limit in 1st paragraph is too much
  - Anders: We should use 2% like the V-T/I-V check
  - Bob: The test loads might drive some buffers out of reasonable range
- We changed it to require matching within 10%
- Bob: Dummy waveforms can be added to facilitate checking
  - Only 2 points needed, but they have to be unrealistic
  - IBISCHK will print calculated numbers
  - Mike: This might fail some IQ checks
    - Bob: Can be commented out, it's just temporary
- Should we scrap this check?
  - Anders: A model failing this has a consistency problem
- We changed the first and last two paragraphs.

Next meeting:

25 Nov 2008 11-12 AM EST (8-9 AM PST)

Meeting ended at 12:08 PM Eastern Time.